Good catch. There's actually a possibility for a similar issues between long vs int in Python2.

Could you change your patch to instead move the PyBool_Check before the PyIn_Check and then add ''continue" into every " if" block in the vector for loop.

I changed the type checks inside the vector loop to else if statements. To me this is the much clearer construct than using if with continue.
If you want I'll readd the PyBool_Check, but it is redundant. In Python2 Bools are also implemented as integers and all we need here is to have an integer value for the bool.

Let's stick with 'continue'. I prefer 'continue', 'break', 'return' in long code blocks like this one because when reading the code, upon encountering 'continue' one can be ensured that even if there was any other code after if...else if...else, it would be skipped. In a sense it keeps readers' focus on the code block at hand only, instead of scrolling up and down a lot.

Fair enough. I changed it to continue.

I noticed another inconsistency in the type conversion. Not sure if this should be tacked on here, made separate or simply ignored.
For the PyInt_Check there is:

long long val = PyInt_AsLong(el);

where as for the PyLong_Check it is:

long val = PyLong_AsLong(el);

For the PyLong it could be

long long val = PyLong_AsLongLong(el);

And simply long type for the PyInt. That would be consistent with the conversions done for the scalars.
But probably doesn't make a difference on most modern systems where long and long long are both 64 bit.